Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-42483: PowerVS: update capi ibmcloud c6bcd313 for 4.17 #9054

Conversation

hamzy
Copy link
Contributor

@hamzy hamzy commented Sep 26, 2024

Update the installer to use commit c6bcd313bce0fc9866e41bb9e3487d9f61c628a3 of cluster-api-provider-ibmcloud
This includes a couple of necessary Transit Gateway fixes.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 26, 2024
@openshift-ci-robot
Copy link
Contributor

@hamzy: This pull request references Jira Issue OCPBUGS-42483, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-42483 to depend on a bug targeting a version in 4.18.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Update the installer to use commit c6bcd313bce0fc9866e41bb9e3487d9f61c628a3 of cluster-api-provider-ibmcloud
This includes a couple of necessary Transit Gateway fixes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@hamzy
Copy link
Contributor Author

hamzy commented Sep 26, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 26, 2024
@openshift-ci-robot
Copy link
Contributor

@hamzy: This pull request references Jira Issue OCPBUGS-42483, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.0) matches configured target version for branch (4.17.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-41938 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-41938 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @juliemathew

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@hamzy
Copy link
Contributor Author

hamzy commented Sep 26, 2024

/assign @r4f4

k8s.io/cloud-provider-vsphere v1.30.1
k8s.io/klog v1.0.0
k8s.io/klog/v2 v2.120.1
k8s.io/utils v0.0.0-20240310230437-4693a0247e57
libvirt.org/go/libvirtxml v1.10002.0
sigs.k8s.io/cluster-api v1.7.3
sigs.k8s.io/cluster-api v1.8.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also bump the capi binary to the same version in cluster-api/cluster-api. Building against one version and running another is asking for trouble.
When we bump, we need to make sure all the other providers still work, so this PR needs to be thoroughly tested.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@r4f4 Updated...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the update. Maybe you forgot to push the new commit?

Copy link
Contributor Author

@hamzy hamzy Sep 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird. It is here locally and was pushed.

hamzy:hamzy-installer$ grep 'sigs.k8s.io/cluster-api v1.8.2' go.mod
	sigs.k8s.io/cluster-api v1.8.2
hamzy:hamzy-installer$ git status
On branch PowerVS-Update-417-CAPI-ibmcloud-c6bcd313
Your branch is up to date with 'origin/PowerVS-Update-417-CAPI-ibmcloud-c6bcd313'.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to also modify cluster-api/cluster-api/go.mod :(
Thanks!

@hamzy hamzy force-pushed the PowerVS-Update-417-CAPI-ibmcloud-c6bcd313 branch from 8a3cf7b to 8536700 Compare September 26, 2024 12:55
@hamzy hamzy force-pushed the PowerVS-Update-417-CAPI-ibmcloud-c6bcd313 branch from 8536700 to 6240605 Compare September 26, 2024 14:29
@hamzy
Copy link
Contributor Author

hamzy commented Sep 26, 2024

/retest-required

@r4f4
Copy link
Contributor

r4f4 commented Sep 26, 2024

/hold

Let's fix the capi mismatch in the master branch first.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 26, 2024
@hamzy
Copy link
Contributor Author

hamzy commented Sep 26, 2024

/test e2e-powervs-ovn

@r4f4
Copy link
Contributor

r4f4 commented Sep 26, 2024

Fix proposed in #9055

@hamzy
Copy link
Contributor Author

hamzy commented Sep 26, 2024

/test e2e-ibmcloud-ovn

@hamzy
Copy link
Contributor Author

hamzy commented Sep 27, 2024

/test e2e-powervs-ovn

Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

@hamzy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-shared-vpc-custom-security-groups 6240605 link false /test e2e-aws-ovn-shared-vpc-custom-security-groups
ci/prow/e2e-aws-ovn-imdsv2 6240605 link false /test e2e-aws-ovn-imdsv2
ci/prow/altinfra-e2e-aws-ovn-localzones 6240605 link false /test altinfra-e2e-aws-ovn-localzones
ci/prow/e2e-aws-ovn-fips 6240605 link false /test e2e-aws-ovn-fips
ci/prow/okd-e2e-agent-ha-dualstack 6240605 link false /test okd-e2e-agent-ha-dualstack
ci/prow/e2e-aws-ovn-heterogeneous 6240605 link false /test e2e-aws-ovn-heterogeneous
ci/prow/okd-e2e-agent-sno-ipv6 6240605 link false /test okd-e2e-agent-sno-ipv6
ci/prow/e2e-aws-ovn-single-node 6240605 link false /test e2e-aws-ovn-single-node
ci/prow/okd-e2e-agent-compact-ipv4 6240605 link false /test okd-e2e-agent-compact-ipv4
ci/prow/e2e-aws-ovn-shared-vpc-edge-zones 6240605 link false /test e2e-aws-ovn-shared-vpc-edge-zones
ci/prow/e2e-aws-ovn-edge-zones 6240605 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-gcp-ovn-byo-vpc 6240605 link false /test e2e-gcp-ovn-byo-vpc
ci/prow/e2e-ibmcloud-ovn 6240605 link false /test e2e-ibmcloud-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@hamzy
Copy link
Contributor Author

hamzy commented Sep 30, 2024

@r4f4 Can this progress now that #9055 has been approved?

@r4f4
Copy link
Contributor

r4f4 commented Sep 30, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 30, 2024
@r4f4
Copy link
Contributor

r4f4 commented Sep 30, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Sep 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4f4

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 30, 2024
@hamzy
Copy link
Contributor Author

hamzy commented Sep 30, 2024

@gpei Hello, could you please label cherry-pick-approved?

@patrickdillon
Copy link
Contributor

/test e2e-openstack-ovn e2e-vsphere-ovn e2e-nutanix-ovn

@patrickdillon
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 30, 2024
@mjturek
Copy link
Contributor

mjturek commented Oct 1, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 1, 2024
@gpei
Copy link
Contributor

gpei commented Oct 5, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 5, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a5919d and 2 for PR HEAD 6240605 in total

@openshift-merge-bot openshift-merge-bot bot merged commit a1b46a5 into openshift:release-4.17 Oct 5, 2024
33 of 43 checks passed
@openshift-ci-robot
Copy link
Contributor

@hamzy: Jira Issue OCPBUGS-42483: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-42483 has been moved to the MODIFIED state.

In response to this:

Update the installer to use commit c6bcd313bce0fc9866e41bb9e3487d9f61c628a3 of cluster-api-provider-ibmcloud
This includes a couple of necessary Transit Gateway fixes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.17.0-202410051335.p0.ga1b46a5.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.17.0-202410051335.p0.ga1b46a5.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.17.0-202410051335.p0.ga1b46a5.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.17.0-202410051335.p0.ga1b46a5.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants